docs: add Tencent Cloud webhook provider#6432
Conversation
|
Welcome @QianChenglong! |
|
Hi @QianChenglong. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Regular contributors should join the org to skip this step. Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@QianChenglong Usually, most of the webhook providers keep their tutorials on their repository. That said, I do not have a strong opinion on that, and I'm ok with that. So let's see what the other maintainers think about this. /ok-to-test |
Coverage Report for CI Build 26032218756Coverage remained the same at 80.634%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsNo coverage regressions found. Coverage Stats
💛 - Coveralls |
|
/lgtm |
|
Why we need a webhook tutorial docs/tutorials/tencentcloud.md in this repo? You could have up-to-date tutorial in the webhook repo, and keep it up to date against different external-dns versions |
Add external-dns-tencentcloud-webhook to the webhook provider table in README.md. Supports DNSPod (public) and PrivateDNS (VPC-scoped) with static credentials or OIDC (TKE RRSA).
9b089fe to
65ab1cb
Compare
|
Thanks for the feedback @ivankatliarchuk. You're right — I've removed the tutorial and kept only the README registry entry. The detailed tutorial lives in the webhook repo itself: https://github.com/tkestack/external-dns-tencentcloud-webhook |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ivankatliarchuk The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What this PR does
Why
The in-tree Tencent Cloud provider was removed per the webhook migration plan. This webhook implementation supports both DNSPod (public DNS) and PrivateDNS (VPC-scoped) with two credential modes:
References